Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d589af3cda6342df288fbcfe451a7b4b3aca6a6a66cbb5aae4b5eee2cfa74ac1

Tx prefix hash: c65bf5ef0e6ce62b99a76b8f8891bba0a656c0cc9a52b1dd398ee91577c7907d
Tx public key: a72138c786a6b52dcf043a70b934eca2af65a0cc8bc18eb6e21c9446ee1bdc49
Timestamp: 1749298234 Timestamp [UCT]: 2025-06-07 12:10:34 Age [y:d:h:m:s]: 00:204:16:41:44
Block: 1299905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144032 RingCT/type: yes/0
Extra: 01a72138c786a6b52dcf043a70b934eca2af65a0cc8bc18eb6e21c9446ee1bdc4902110000000943846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f8ab5bc51817c52cd65ec5a12461141bec028c5b138e091f5eab9f50ccbe540 0.600000000000 1787448 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": 1299915, "vin": [ { "gen": { "height": 1299905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f8ab5bc51817c52cd65ec5a12461141bec028c5b138e091f5eab9f50ccbe540" } } ], "extra": [ 1, 167, 33, 56, 199, 134, 166, 181, 45, 207, 4, 58, 112, 185, 52, 236, 162, 175, 101, 160, 204, 139, 193, 142, 182, 226, 28, 148, 70, 238, 27, 220, 73, 2, 17, 0, 0, 0, 9, 67, 132, 109, 102, 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