Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fe1f0fa10bb621235bef1d4665d8641d415ab62ac5d1e7a4b61b65dc1c176900

Tx prefix hash: 887e7be2dd8dd12fe0996e77684d4662d33d9a4bc0398b2c09e074830e1af6d9
Tx public key: c9f89973d9c8cb865c1c97dfbf07e4a295c2a30ba953dc3738cf857a50e6f4fc
Timestamp: 1736714492 Timestamp [UCT]: 2025-01-12 20:41:32 Age [y:d:h:m:s]: 00:065:14:36:26
Block: 1195980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46686 RingCT/type: yes/0
Extra: 01c9f89973d9c8cb865c1c97dfbf07e4a295c2a30ba953dc3738cf857a50e6f4fc0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78e38f55b9f1000d880acda0b4f5f621bd62fa3d5170ec22b30cefbdf9660df9 0.600000000000 1682577 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1195990, "vin": [ { "gen": { "height": 1195980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78e38f55b9f1000d880acda0b4f5f621bd62fa3d5170ec22b30cefbdf9660df9" } } ], "extra": [ 1, 201, 248, 153, 115, 217, 200, 203, 134, 92, 28, 151, 223, 191, 7, 228, 162, 149, 194, 163, 11, 169, 83, 220, 55, 56, 207, 133, 122, 80, 230, 244, 252, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8