Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc74d5f318684dce58105035bf6cea3fdc1d9f309184dc2cce4eb14d544ec80

Tx prefix hash: 6d3598a4a69508ab10768c68c701905ce251d945fb31bb182bce998614aee974
Tx public key: add2fbbb58b4031c0b2a2d470d57770260c5831e4c55a90caef7e8ca930f4dd5
Timestamp: 1699871740 Timestamp [UCT]: 2023-11-13 10:35:40 Age [y:d:h:m:s]: 01:214:12:13:12
Block: 890689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414447 RingCT/type: yes/0
Extra: 01add2fbbb58b4031c0b2a2d470d57770260c5831e4c55a90caef7e8ca930f4dd502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.686716682000 dcy

stealth address amount amount idx
00: cd07a256e8c59566d9c1e3edfa3e1b9f1eef13a3d408935a9eaa0758cda9466b 0.686716682000 1346718 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": 890699, "vin": [ { "gen": { "height": 890689 } } ], "vout": [ { "amount": 686716682, "target": { "key": "cd07a256e8c59566d9c1e3edfa3e1b9f1eef13a3d408935a9eaa0758cda9466b" } } ], "extra": [ 1, 173, 210, 251, 187, 88, 180, 3, 28, 11, 42, 45, 71, 13, 87, 119, 2, 96, 197, 131, 30, 76, 85, 169, 12, 174, 247, 232, 202, 147, 15, 77, 213, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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