Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da0f664af5fa1c81b15596073361f34ba529b80a7fbb4c9ead5ff31c2ddb1a1d

Tx prefix hash: 9d5e54565bde114880fa1b6bb70793c78bc9ec544104c7e67ea09c85fe52844e
Tx public key: 1b6db7385b4f1caa7bcafb7c7b00795c67f53c6d1e05b2d6cd2f1a51e448979f
Timestamp: 1747807795 Timestamp [UCT]: 2025-05-21 06:09:55 Age [y:d:h:m:s]: 00:256:05:46:02
Block: 1287566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180741 RingCT/type: yes/0
Extra: 011b6db7385b4f1caa7bcafb7c7b00795c67f53c6d1e05b2d6cd2f1a51e448979f02110000000f1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60e41300a4cbea7fa32aac7c5abd3ad9aafb94b2a92374e9df783d8d6426bf0b 0.600000000000 1775033 of 15

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": 1287576, "vin": [ { "gen": { "height": 1287566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60e41300a4cbea7fa32aac7c5abd3ad9aafb94b2a92374e9df783d8d6426bf0b" } } ], "extra": [ 1, 27, 109, 183, 56, 91, 79, 28, 170, 123, 202, 251, 124, 123, 0, 121, 92, 103, 245, 60, 109, 30, 5, 178, 214, 205, 47, 26, 81, 228, 72, 151, 159, 2, 17, 0, 0, 0, 15, 31, 144, 81, 122, 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