Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7235bcc489eaa81dfc346e9016b28ac14f54bdad847d7a7fc7be24fe8411d187

Tx prefix hash: a95f68e4a2b55698df58ea202cbffe2ae83c9e87e77ec6fb65aab4d3158bdf39
Tx public key: 71416b69c8f73efc99ef711519afa95175b2afdb47783952acb60a0dcd7217d0
Timestamp: 1694603135 Timestamp [UCT]: 2023-09-13 11:05:35 Age [y:d:h:m:s]: 01:204:20:52:46
Block: 847186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407517 RingCT/type: yes/0
Extra: 0171416b69c8f73efc99ef711519afa95175b2afdb47783952acb60a0dcd7217d0021100000008faf35c9c000000000000000000

1 output(s) for total of 0.957020320000 dcy

stealth address amount amount idx
00: bc21e1141f5a696c075c80399a6a6e93fb116465ff7e2e3ceff95c9b1feadbd1 0.957020320000 1300690 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": 847196, "vin": [ { "gen": { "height": 847186 } } ], "vout": [ { "amount": 957020320, "target": { "key": "bc21e1141f5a696c075c80399a6a6e93fb116465ff7e2e3ceff95c9b1feadbd1" } } ], "extra": [ 1, 113, 65, 107, 105, 200, 247, 62, 252, 153, 239, 113, 21, 25, 175, 169, 81, 117, 178, 175, 219, 71, 120, 57, 82, 172, 182, 10, 13, 205, 114, 23, 208, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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