Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a555ae470ae8edc6170596892843fb85acfa5c2c3fc62ce189daaf65d472a0

Tx prefix hash: 275925b832e95245cf89aedfdc8592ec0e7be7904d98a85a06089a184ebd6f31
Tx public key: 28e8c6721eea78353cb68bd6e7fba0575be20c4a0d4e4431ac762dedb9c6f091
Timestamp: 1723295420 Timestamp [UCT]: 2024-08-10 13:10:20 Age [y:d:h:m:s]: 00:225:03:56:10
Block: 1084880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160807 RingCT/type: yes/0
Extra: 0128e8c6721eea78353cb68bd6e7fba0575be20c4a0d4e4431ac762dedb9c6f091021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c8e1057163c4a35a1649b05be955ea26135548ca1146f0b11fb24a709eb95d0 0.600000000000 1559311 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": 1084890, "vin": [ { "gen": { "height": 1084880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c8e1057163c4a35a1649b05be955ea26135548ca1146f0b11fb24a709eb95d0" } } ], "extra": [ 1, 40, 232, 198, 114, 30, 234, 120, 53, 60, 182, 139, 214, 231, 251, 160, 87, 91, 226, 12, 74, 13, 78, 68, 49, 172, 118, 45, 237, 185, 198, 240, 145, 2, 17, 0, 0, 0, 1, 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