Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab9f45e0d351216f3558092da8a0b1778e16cc6dd433163fab71a6cde9c1efab

Tx prefix hash: 027f7c9973d89bebb9d8876499b2db77f4ea7f2b09ac20ff2945d6f39d440825
Tx public key: 271fb9fc72dab5ec7d82fb16e8ee0de42498145c5be7fe03450cf55f4fc9e6ef
Timestamp: 1626821641 Timestamp [UCT]: 2021-07-20 22:54:01 Age [y:d:h:m:s]: 03:166:22:42:45
Block: 297838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 891021 RingCT/type: yes/0
Extra: 01271fb9fc72dab5ec7d82fb16e8ee0de42498145c5be7fe03450cf55f4fc9e6ef0211000000176367b7e9000000000000000000

1 output(s) for total of 63.261511059000 dcy

stealth address amount amount idx
00: cd0035e884b714d6b123352a5d61812740c059ce37e4f6a2c0051496cc5679fe 63.261511059000 623329 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": 297848, "vin": [ { "gen": { "height": 297838 } } ], "vout": [ { "amount": 63261511059, "target": { "key": "cd0035e884b714d6b123352a5d61812740c059ce37e4f6a2c0051496cc5679fe" } } ], "extra": [ 1, 39, 31, 185, 252, 114, 218, 181, 236, 125, 130, 251, 22, 232, 238, 13, 228, 36, 152, 20, 92, 91, 231, 254, 3, 69, 12, 245, 95, 79, 201, 230, 239, 2, 17, 0, 0, 0, 23, 99, 103, 183, 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