Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dba59820022e9c99ee442e8be308e6a054d680cd97e8d343e1a5a0540fbd5b43

Tx prefix hash: 148776059d952e0cd244fd2ecfe7eb7faa470d7cc08677dd9bf4b43730bc8238
Tx public key: e9f3bd15c07dcb2d7f77bea5c9a0b6e071305caaa38ddc445810f3cf9aa706ed
Timestamp: 1687508565 Timestamp [UCT]: 2023-06-23 08:22:45 Age [y:d:h:m:s]: 01:146:00:01:14
Block: 788441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365679 RingCT/type: yes/0
Extra: 01e9f3bd15c07dcb2d7f77bea5c9a0b6e071305caaa38ddc445810f3cf9aa706ed02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.498193182000 dcy

stealth address amount amount idx
00: 094af5df2a77f3f8bf3e44f8df26239f10d3021e350c4dac5d318c0e17451dbb 1.498193182000 1238546 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": 788451, "vin": [ { "gen": { "height": 788441 } } ], "vout": [ { "amount": 1498193182, "target": { "key": "094af5df2a77f3f8bf3e44f8df26239f10d3021e350c4dac5d318c0e17451dbb" } } ], "extra": [ 1, 233, 243, 189, 21, 192, 125, 203, 45, 127, 119, 190, 165, 201, 160, 182, 224, 113, 48, 92, 170, 163, 141, 220, 68, 88, 16, 243, 207, 154, 167, 6, 237, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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