Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 427a5345e45d6952351ac1f6911d29bc37b09d507018cd1d62a9470c0579ce83

Tx prefix hash: 77613f86e02db3c988c02d04bb0dc0fd1ae425f2a85b6617a60cf3bc06c4be0b
Tx public key: cafa57dab9996faf241355dcfa9a57978c2f3aee628a971c227c2503071f8253
Timestamp: 1721841261 Timestamp [UCT]: 2024-07-24 17:14:21 Age [y:d:h:m:s]: 00:181:22:25:28
Block: 1072813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130133 RingCT/type: yes/0
Extra: 01cafa57dab9996faf241355dcfa9a57978c2f3aee628a971c227c2503071f8253021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 366e5fed82bf9bf69c66ef0a5b74ae3d1226bb2ae13bf4f105da65219e76b12a 0.600000000000 1545310 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": 1072823, "vin": [ { "gen": { "height": 1072813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "366e5fed82bf9bf69c66ef0a5b74ae3d1226bb2ae13bf4f105da65219e76b12a" } } ], "extra": [ 1, 202, 250, 87, 218, 185, 153, 111, 175, 36, 19, 85, 220, 250, 154, 87, 151, 140, 47, 58, 238, 98, 138, 151, 28, 34, 124, 37, 3, 7, 31, 130, 83, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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