Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 174dde24e0aeaa0b7664d6b3d3c0a0c349b299fa2a00e60f2e490ca9f0fe09c0

Tx prefix hash: 878862e3304d463740134357b62feb93196607c00a9313344dd439fd56ba02c3
Tx public key: a8a3f865c30959552b1bbed97b4f78f9803a3263bf37a167f7d913a65e5388b5
Timestamp: 1694091849 Timestamp [UCT]: 2023-09-07 13:04:09 Age [y:d:h:m:s]: 01:140:00:03:31
Block: 842952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361353 RingCT/type: yes/0
Extra: 01a8a3f865c30959552b1bbed97b4f78f9803a3263bf37a167f7d913a65e5388b502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.988439665000 dcy

stealth address amount amount idx
00: 7347292b371d43ff7b242c76f29bbec695850b930e54dc774422bb40b861001b 0.988439665000 1296126 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": 842962, "vin": [ { "gen": { "height": 842952 } } ], "vout": [ { "amount": 988439665, "target": { "key": "7347292b371d43ff7b242c76f29bbec695850b930e54dc774422bb40b861001b" } } ], "extra": [ 1, 168, 163, 248, 101, 195, 9, 89, 85, 43, 27, 190, 217, 123, 79, 120, 249, 128, 58, 50, 99, 191, 55, 161, 103, 247, 217, 19, 166, 94, 83, 136, 181, 2, 17, 0, 0, 0, 7, 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