Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd43d71c6a96db4d965c5e10836a07d2dd0551589f23e329eb713bb9ec3c346f

Tx prefix hash: cf9e48728111bcb241fed6d626c82f68028a8ba1255601ab3c8233db974baff3
Tx public key: 8dda98f2c8c0edc86233c49ccdba6eeaf4e95b0054c6c454d321d01e8d3a961b
Timestamp: 1719416032 Timestamp [UCT]: 2024-06-26 15:33:52 Age [y:d:h:m:s]: 00:322:12:02:43
Block: 1052706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230477 RingCT/type: yes/0
Extra: 018dda98f2c8c0edc86233c49ccdba6eeaf4e95b0054c6c454d321d01e8d3a961b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f82f27f6c8a91cc4e871ac4841e67fbb9d913b26a4055cebda1a7e4f35520d08 0.600000000000 1523037 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": 1052716, "vin": [ { "gen": { "height": 1052706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f82f27f6c8a91cc4e871ac4841e67fbb9d913b26a4055cebda1a7e4f35520d08" } } ], "extra": [ 1, 141, 218, 152, 242, 200, 192, 237, 200, 98, 51, 196, 156, 205, 186, 110, 234, 244, 233, 91, 0, 84, 198, 196, 84, 211, 33, 208, 30, 141, 58, 150, 27, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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