Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a82dea781fbf5d1c0bf1eddb633707763f5dd69844861fdbd162b08d9a4d7ab9

Tx prefix hash: 996ba54fcf7b2917f9797e84723da6725e6183c91b0d16ae3863cb68e4f00e0b
Tx public key: eb8858f270c74246f3ab9190c2deae0c7b8a522e1129d37d7180b5eed0c9f0d9
Timestamp: 1724203771 Timestamp [UCT]: 2024-08-21 01:29:31 Age [y:d:h:m:s]: 00:232:09:20:03
Block: 1092413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165955 RingCT/type: yes/0
Extra: 01eb8858f270c74246f3ab9190c2deae0c7b8a522e1129d37d7180b5eed0c9f0d9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecb563dc14d9882600f2d4f23b1fccbe18bdb74ab1ec714b66276901bfbf51b9 0.600000000000 1567154 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": 1092423, "vin": [ { "gen": { "height": 1092413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecb563dc14d9882600f2d4f23b1fccbe18bdb74ab1ec714b66276901bfbf51b9" } } ], "extra": [ 1, 235, 136, 88, 242, 112, 199, 66, 70, 243, 171, 145, 144, 194, 222, 174, 12, 123, 138, 82, 46, 17, 41, 211, 125, 113, 128, 181, 238, 208, 201, 240, 217, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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