Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bebd5e6ba5d77cd611df13b679d2827d48deb989cdfc909431e16d88025add3

Tx prefix hash: b441c2c7fe03baea6531b99baebfe89c0348facb11adb2a4ae7f3cf0118e1831
Tx public key: ab6f62476767cf9c112bb10eda46c0e1c6025920f4c65b0ca18caf0cc9b2648e
Timestamp: 1749718165 Timestamp [UCT]: 2025-06-12 08:49:25 Age [y:d:h:m:s]: 00:151:12:44:57
Block: 1303337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106014 RingCT/type: yes/0
Extra: 01ab6f62476767cf9c112bb10eda46c0e1c6025920f4c65b0ca18caf0cc9b2648e021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e462bbd4881e6ec2b13165889fda812e6d90bd2a2b5b4b4d8e2088473f97a9c 0.600000000000 1790916 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": 1303347, "vin": [ { "gen": { "height": 1303337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e462bbd4881e6ec2b13165889fda812e6d90bd2a2b5b4b4d8e2088473f97a9c" } } ], "extra": [ 1, 171, 111, 98, 71, 103, 103, 207, 156, 17, 43, 177, 14, 218, 70, 192, 225, 198, 2, 89, 32, 244, 198, 91, 12, 161, 140, 175, 12, 201, 178, 100, 142, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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