Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da4b2f9b04efb324f0e80f1b41d2cec9a7aa1dca0375e3bf4d1b8bbcd74f6440

Tx prefix hash: 5ed34e65304de2799d19eb975fd0115547bfe6c702ff4808a862e2b2d1610c62
Tx public key: bdfe3ceb002f0cb68f20b5c51d0127aab3a75d47ca0b0c6150646307919c830c
Timestamp: 1713836711 Timestamp [UCT]: 2024-04-23 01:45:11 Age [y:d:h:m:s]: 01:192:07:31:47
Block: 1006461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396109 RingCT/type: yes/0
Extra: 01bdfe3ceb002f0cb68f20b5c51d0127aab3a75d47ca0b0c6150646307919c830c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8cd01177fd0f8f9d1c36a89dc7ebd32df5cf4b851053877e5279b928f9688da 0.600000000000 1467499 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": 1006471, "vin": [ { "gen": { "height": 1006461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8cd01177fd0f8f9d1c36a89dc7ebd32df5cf4b851053877e5279b928f9688da" } } ], "extra": [ 1, 189, 254, 60, 235, 0, 47, 12, 182, 143, 32, 181, 197, 29, 1, 39, 170, 179, 167, 93, 71, 202, 11, 12, 97, 80, 100, 99, 7, 145, 156, 131, 12, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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