Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5b4e2442d22ce46ffaa3d85a8dd80350c970e44b9cf7ecabce7cc7ee0dffd0

Tx prefix hash: 9dcdaaaa0c4d8acd928007ccc4ca8d323b7e22faeeee66dbf06f2a78c9e0fd19
Tx public key: 4046558d45a8ace8997769912e5ef70988c86a6edb6033df114b38d1c29944c4
Timestamp: 1582644550 Timestamp [UCT]: 2020-02-25 15:29:10 Age [y:d:h:m:s]: 04:325:11:48:15
Block: 72364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125243 RingCT/type: yes/0
Extra: 014046558d45a8ace8997769912e5ef70988c86a6edb6033df114b38d1c29944c4021100000002026b59f3000000000000000000

1 output(s) for total of 353.379300004000 dcy

stealth address amount amount idx
00: 72f3c60f8efbc3060b081696111d4a6ffb0d080d71d9ff4440801f146043feb8 353.379300004000 133587 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": 72374, "vin": [ { "gen": { "height": 72364 } } ], "vout": [ { "amount": 353379300004, "target": { "key": "72f3c60f8efbc3060b081696111d4a6ffb0d080d71d9ff4440801f146043feb8" } } ], "extra": [ 1, 64, 70, 85, 141, 69, 168, 172, 232, 153, 119, 105, 145, 46, 94, 247, 9, 136, 200, 106, 110, 219, 96, 51, 223, 17, 75, 56, 209, 194, 153, 68, 196, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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