Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad125b482b13e7f812eb4c6f1751da9d7ae154531cf6e780650534b79ced5c5

Tx prefix hash: 6318ccfbc9be0ff0cf1589c52938fe91bfd1861ae318fbb2867d173769ceb6d4
Tx public key: 41cbaa57d50511863ec14155c97a2bf1f236cda67075a03e48eaa3bfdac36ce9
Timestamp: 1714432862 Timestamp [UCT]: 2024-04-29 23:21:02 Age [y:d:h:m:s]: 00:353:05:48:12
Block: 1011388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252531 RingCT/type: yes/0
Extra: 0141cbaa57d50511863ec14155c97a2bf1f236cda67075a03e48eaa3bfdac36ce90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 007f2c8cf457a497f4cf20e80918777659b3e1c1d2bfa2478d7fa277238b9721 0.600000000000 1473606 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": 1011398, "vin": [ { "gen": { "height": 1011388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "007f2c8cf457a497f4cf20e80918777659b3e1c1d2bfa2478d7fa277238b9721" } } ], "extra": [ 1, 65, 203, 170, 87, 213, 5, 17, 134, 62, 193, 65, 85, 201, 122, 43, 241, 242, 54, 205, 166, 112, 117, 160, 62, 72, 234, 163, 191, 218, 195, 108, 233, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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