Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794f8b79033df3878b29e771c7dac5407dc31da81d1fa5511b3753e7299eb1ce

Tx prefix hash: 7ff675ba0d7537ba1305d5830ac6485091c32f8823263309a420cfde31022c8a
Tx public key: c4d3ea9ba7352578b152fe58f8d5d91601c80efde7c62a13bce33bbb5bcc7c4c
Timestamp: 1695603354 Timestamp [UCT]: 2023-09-25 00:55:54 Age [y:d:h:m:s]: 01:152:22:01:50
Block: 855494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370320 RingCT/type: yes/0
Extra: 01c4d3ea9ba7352578b152fe58f8d5d91601c80efde7c62a13bce33bbb5bcc7c4c0211000000054b8f5122000000000000000000

1 output(s) for total of 0.898241868000 dcy

stealth address amount amount idx
00: 72898f8256b13f5040f503673b98150b855b1964a2e40f0692e6e7f3cf9f002d 0.898241868000 1309518 of 0

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": 855504, "vin": [ { "gen": { "height": 855494 } } ], "vout": [ { "amount": 898241868, "target": { "key": "72898f8256b13f5040f503673b98150b855b1964a2e40f0692e6e7f3cf9f002d" } } ], "extra": [ 1, 196, 211, 234, 155, 167, 53, 37, 120, 177, 82, 254, 88, 248, 213, 217, 22, 1, 200, 14, 253, 231, 198, 42, 19, 188, 227, 59, 187, 91, 204, 124, 76, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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