Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 661ce0d0fc791c5375f82db9fc502c3ff7ea85f5c54ddb0f4af6d6829d4613b3

Tx prefix hash: 5deacbae903ed322590fef8a53ae3f152e527bc62d9f4b86042ad47410fdce26
Tx public key: 8d859237298283585656c72f2a1abe9cb105938ac0fdf212d7ca29bb0c04400b
Timestamp: 1742249920 Timestamp [UCT]: 2025-03-17 22:18:40 Age [y:d:h:m:s]: 00:248:16:23:50
Block: 1241560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175454 RingCT/type: yes/0
Extra: 018d859237298283585656c72f2a1abe9cb105938ac0fdf212d7ca29bb0c04400b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae04e38868155623670ddd95da30ae2f60f22ed1f2b548bf20974eb2138713e 0.600000000000 1728533 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": 1241570, "vin": [ { "gen": { "height": 1241560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae04e38868155623670ddd95da30ae2f60f22ed1f2b548bf20974eb2138713e" } } ], "extra": [ 1, 141, 133, 146, 55, 41, 130, 131, 88, 86, 86, 199, 47, 42, 26, 190, 156, 177, 5, 147, 138, 192, 253, 242, 18, 215, 202, 41, 187, 12, 4, 64, 11, 2, 17, 0, 0, 0, 5, 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