Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cce4d496e161e5955577a09e4b9324eb5258f32f35bc30fe8f694efaa3525e0

Tx prefix hash: d3c0a97810744edfca9338b70282276640fdf1c04abf91313d5a1b1aaf35ba86
Tx public key: e90aa0061c4b087124ad92ba684977a34bcc6825d1e3542e51494da4bc91f811
Timestamp: 1695470565 Timestamp [UCT]: 2023-09-23 12:02:45 Age [y:d:h:m:s]: 01:204:06:18:49
Block: 854389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407066 RingCT/type: yes/0
Extra: 01e90aa0061c4b087124ad92ba684977a34bcc6825d1e3542e51494da4bc91f811021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.905846518000 dcy

stealth address amount amount idx
00: fc797f8a7c9ea294389645ddf7c238a63aea55f7568db6e92edd32f7d0b50bb1 0.905846518000 1308359 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": 854399, "vin": [ { "gen": { "height": 854389 } } ], "vout": [ { "amount": 905846518, "target": { "key": "fc797f8a7c9ea294389645ddf7c238a63aea55f7568db6e92edd32f7d0b50bb1" } } ], "extra": [ 1, 233, 10, 160, 6, 28, 75, 8, 113, 36, 173, 146, 186, 104, 73, 119, 163, 75, 204, 104, 37, 209, 227, 84, 46, 81, 73, 77, 164, 188, 145, 248, 17, 2, 17, 0, 0, 0, 3, 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