Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 056097c47bbb487bc72cde7e170b82fc20fe0ed3cb2b7baf3748a38b3c37f250

Tx prefix hash: 00b59efe31ad11fe213e4a9c04967c16341c645e5aa2a45fe34cf2bf522bd910
Tx public key: f52b0d607dc0b81936ab31848e2ca1c6c47c9c2d75efb19d25d4e215ef63b060
Timestamp: 1723429526 Timestamp [UCT]: 2024-08-12 02:25:26 Age [y:d:h:m:s]: 00:255:07:24:45
Block: 1085983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182368 RingCT/type: yes/0
Extra: 01f52b0d607dc0b81936ab31848e2ca1c6c47c9c2d75efb19d25d4e215ef63b06002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ec4d2fff521e02668dc2600f23781228792f28b5794569121bef1c88fd6be29 0.600000000000 1560574 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": 1085993, "vin": [ { "gen": { "height": 1085983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ec4d2fff521e02668dc2600f23781228792f28b5794569121bef1c88fd6be29" } } ], "extra": [ 1, 245, 43, 13, 96, 125, 192, 184, 25, 54, 171, 49, 132, 142, 44, 161, 198, 196, 124, 156, 45, 117, 239, 177, 157, 37, 212, 226, 21, 239, 99, 176, 96, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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