Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d7f99ea00df232da53dc5356263694554330b4bb2b157120592bbd78daf2f41

Tx prefix hash: ee5c1d9e33e5d109497b37d5d7e9163684a0048c89a60a0b6cf35d98d8fe126f
Tx public key: 03094cacf48ebee079fe6e79d49de4a006cdb382f02e6da21c2c82b8f43837fd
Timestamp: 1754647651 Timestamp [UCT]: 2025-08-08 10:07:31 Age [y:d:h:m:s]: 00:102:23:30:46
Block: 1342738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72694 RingCT/type: yes/0
Extra: 0103094cacf48ebee079fe6e79d49de4a006cdb382f02e6da21c2c82b8f43837fd021100000015ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04c5d847226218ab67c619153193d209d7e0469d97809a6c0533bc6c2b21c2ab 0.600000000000 1830571 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": 1342748, "vin": [ { "gen": { "height": 1342738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04c5d847226218ab67c619153193d209d7e0469d97809a6c0533bc6c2b21c2ab" } } ], "extra": [ 1, 3, 9, 76, 172, 244, 142, 190, 224, 121, 254, 110, 121, 212, 157, 228, 160, 6, 205, 179, 130, 240, 46, 109, 162, 28, 44, 130, 184, 244, 56, 55, 253, 2, 17, 0, 0, 0, 21, 173, 121, 72, 208, 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