Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9618642af027ae3bc6926e3cd40fed8ecc116bfb7dcb9e2402e0308e4d7b37c1

Tx prefix hash: 72279da2c4db2d8175712bbb47b52c163fb5e1448e1b3b90e3e57198d1891fea
Tx public key: 03c873b74254f23b0a1f7cdaa58faf76811e0f1ce4c5f55239caefe28b498096
Timestamp: 1736549548 Timestamp [UCT]: 2025-01-10 22:52:28 Age [y:d:h:m:s]: 00:158:13:35:40
Block: 1194614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113043 RingCT/type: yes/0
Extra: 0103c873b74254f23b0a1f7cdaa58faf76811e0f1ce4c5f55239caefe28b498096021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6343c73941ba7ca63e4386832011287c75fe832504a9f596897c2cadc709f2d7 0.600000000000 1681191 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": 1194624, "vin": [ { "gen": { "height": 1194614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6343c73941ba7ca63e4386832011287c75fe832504a9f596897c2cadc709f2d7" } } ], "extra": [ 1, 3, 200, 115, 183, 66, 84, 242, 59, 10, 31, 124, 218, 165, 143, 175, 118, 129, 30, 15, 28, 228, 197, 245, 82, 57, 202, 239, 226, 139, 73, 128, 150, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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