Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 991b7bde20e4de0a5ca1fdd821ec63927f7a915377dcc9da52132417df22fd3e

Tx prefix hash: 88b338056fe7bd8b355e9082a3a04bb6c3f84024d589a19f8f53a161668ce27f
Tx public key: 6d569a44702f8711f360123941aa49a49305a5937b92fd92a79bfa462f7c8596
Timestamp: 1713741048 Timestamp [UCT]: 2024-04-21 23:10:48 Age [y:d:h:m:s]: 01:051:23:23:57
Block: 1005657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298081 RingCT/type: yes/0
Extra: 016d569a44702f8711f360123941aa49a49305a5937b92fd92a79bfa462f7c85960211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 340c274fffb444f585bc13993201e4b27e5b6ccf1a2177f6a41d68cf3f22a0e0 0.600000000000 1466415 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": 1005667, "vin": [ { "gen": { "height": 1005657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "340c274fffb444f585bc13993201e4b27e5b6ccf1a2177f6a41d68cf3f22a0e0" } } ], "extra": [ 1, 109, 86, 154, 68, 112, 47, 135, 17, 243, 96, 18, 57, 65, 170, 73, 164, 147, 5, 165, 147, 123, 146, 253, 146, 167, 155, 250, 70, 47, 124, 133, 150, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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