Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d687e7989505dc3ff3cd1d5436fcc5054dc707dd70fb8ee5587e58deebf2d28

Tx prefix hash: 2c6d5585f4fdffaa3158f9abfbbc68bd9bb9d3f1ba131e56dd4e78395c4114f5
Tx public key: 2382460a811ac314aed3ce841fff01a3f8a9d166bd93188713c4b547d9495b8a
Timestamp: 1708291756 Timestamp [UCT]: 2024-02-18 21:29:16 Age [y:d:h:m:s]: 01:339:06:55:18
Block: 960494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501189 RingCT/type: yes/0
Extra: 012382460a811ac314aed3ce841fff01a3f8a9d166bd93188713c4b547d9495b8a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c67e7688608b57ba83adab19b06e1c11e6fd9722162c0015385f7763b9489593 0.600000000000 1420065 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": 960504, "vin": [ { "gen": { "height": 960494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c67e7688608b57ba83adab19b06e1c11e6fd9722162c0015385f7763b9489593" } } ], "extra": [ 1, 35, 130, 70, 10, 129, 26, 195, 20, 174, 211, 206, 132, 31, 255, 1, 163, 248, 169, 209, 102, 189, 147, 24, 135, 19, 196, 181, 71, 217, 73, 91, 138, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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