Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56dbefb7d5e9625ee779422f73ae53902d9ee27ced37d42d613f030bbbba4876

Tx prefix hash: 5752ca9c90f5b9fdd47b99a61c83d4b3251b7f0334846f5b3fe28a357f8fc3d0
Tx public key: 29e34f023e29396a0b3988a467cb215ec80f45b30c23f5bb2d1ae751f2f0efba
Timestamp: 1677023924 Timestamp [UCT]: 2023-02-21 23:58:44 Age [y:d:h:m:s]: 02:003:17:35:40
Block: 702142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524224 RingCT/type: yes/0
Extra: 0129e34f023e29396a0b3988a467cb215ec80f45b30c23f5bb2d1ae751f2f0efba02110000000174b6d784000000000000000000

1 output(s) for total of 2.894089724000 dcy

stealth address amount amount idx
00: e6d50145c882bb7a7bd20b6dcfd7df6e0bc2ba81a76358b4ae412fb25c2c545b 2.894089724000 1145641 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": 702152, "vin": [ { "gen": { "height": 702142 } } ], "vout": [ { "amount": 2894089724, "target": { "key": "e6d50145c882bb7a7bd20b6dcfd7df6e0bc2ba81a76358b4ae412fb25c2c545b" } } ], "extra": [ 1, 41, 227, 79, 2, 62, 41, 57, 106, 11, 57, 136, 164, 103, 203, 33, 94, 200, 15, 69, 179, 12, 35, 245, 187, 45, 26, 231, 81, 242, 240, 239, 186, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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