Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38eeba6fc0f18a7a3d56effb81bbb52de6314289fc809e97fe2c3fe13d9577cc

Tx prefix hash: 44b821c80f4e2f74b4329102289e16c2b0b834a793a87e0a963868f837d4d2d6
Tx public key: 6b8d04ea01ec7757b91e6fd64d427dca1309cfc4ac18af64ab47dab904621e14
Timestamp: 1746755635 Timestamp [UCT]: 2025-05-09 01:53:55 Age [y:d:h:m:s]: 00:201:13:18:25
Block: 1278839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141778 RingCT/type: yes/0
Extra: 016b8d04ea01ec7757b91e6fd64d427dca1309cfc4ac18af64ab47dab904621e140211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd29c097e7664437397d934c1bf6bacb3ad184a2e65b72aba3c2b969a9976cc8 0.600000000000 1766210 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": 1278849, "vin": [ { "gen": { "height": 1278839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd29c097e7664437397d934c1bf6bacb3ad184a2e65b72aba3c2b969a9976cc8" } } ], "extra": [ 1, 107, 141, 4, 234, 1, 236, 119, 87, 185, 30, 111, 214, 77, 66, 125, 202, 19, 9, 207, 196, 172, 24, 175, 100, 171, 71, 218, 185, 4, 98, 30, 20, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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