Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ed6fcd40e564c358e8b488e4f9217a68919c9fcc397e8065ed5f52babd54940

Tx prefix hash: fcbe2f5dbff6dce24d7f992b8e80d08855cdb9ba5b065527e93569b156841174
Tx public key: f73e03bc050d4cd0df8df8aeff5dd8ab91fac5aa236f77224704f1fd6bc99e83
Timestamp: 1765238168 Timestamp [UCT]: 2025-12-08 23:56:08 Age [y:d:h:m:s]: 00:030:14:16:38
Block: 1429464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21917 RingCT/type: yes/0
Extra: 01f73e03bc050d4cd0df8df8aeff5dd8ab91fac5aa236f77224704f1fd6bc99e83021100000010d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d3113cc551e7d0145fb8154e81687ebfd656e7be41beee57e60aa514ab55ff2 0.600000000000 1918193 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": 1429474, "vin": [ { "gen": { "height": 1429464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d3113cc551e7d0145fb8154e81687ebfd656e7be41beee57e60aa514ab55ff2" } } ], "extra": [ 1, 247, 62, 3, 188, 5, 13, 76, 208, 223, 141, 248, 174, 255, 93, 216, 171, 145, 250, 197, 170, 35, 111, 119, 34, 71, 4, 241, 253, 107, 201, 158, 131, 2, 17, 0, 0, 0, 16, 214, 225, 157, 124, 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