Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1305437dfac6578999fe96645b0eaeb5c401ce60ef8ed068d62610d5abf12d

Tx prefix hash: d7801f57f41a528b74db6ab9479975848152a9f2225c6726eb872b437748330c
Tx public key: e871c3ea2a08feb2581df1e526609e9615f8fa843efdb91cf9f7037641e36d37
Timestamp: 1684576334 Timestamp [UCT]: 2023-05-20 09:52:14 Age [y:d:h:m:s]: 02:174:09:46:26
Block: 764135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 644447 RingCT/type: yes/0
Extra: 01e871c3ea2a08feb2581df1e526609e9615f8fa843efdb91cf9f7037641e36d37021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.803448396000 dcy

stealth address amount amount idx
00: e22dc223864444223ae9e9bf09a65f7dc0c664902629911467dc88bdfa3c5e06 1.803448396000 1213030 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": 764145, "vin": [ { "gen": { "height": 764135 } } ], "vout": [ { "amount": 1803448396, "target": { "key": "e22dc223864444223ae9e9bf09a65f7dc0c664902629911467dc88bdfa3c5e06" } } ], "extra": [ 1, 232, 113, 195, 234, 42, 8, 254, 178, 88, 29, 241, 229, 38, 96, 158, 150, 21, 248, 250, 132, 62, 253, 185, 28, 249, 247, 3, 118, 65, 227, 109, 55, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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