Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31945fd8e791a070f0ebf6f9bae17fb64a764d419d7138d638a9abb57fdcdab3

Tx prefix hash: cd690900a30ed3f5648d49ddac257ea0bc64b17eda0df43c8cd4fd5240c467a3
Tx public key: d6700a913aed6986127cd38d1d9887d7c6f442e9ff539e1134241bfe9dcf14e5
Timestamp: 1746434230 Timestamp [UCT]: 2025-05-05 08:37:10 Age [y:d:h:m:s]: 00:187:15:06:50
Block: 1276184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131798 RingCT/type: yes/0
Extra: 01d6700a913aed6986127cd38d1d9887d7c6f442e9ff539e1134241bfe9dcf14e50211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a98d740868e4c97f08a6af433a8d2a207d9bf7e3c9f1626d4157537e3e05197 0.600000000000 1763509 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": 1276194, "vin": [ { "gen": { "height": 1276184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a98d740868e4c97f08a6af433a8d2a207d9bf7e3c9f1626d4157537e3e05197" } } ], "extra": [ 1, 214, 112, 10, 145, 58, 237, 105, 134, 18, 124, 211, 141, 29, 152, 135, 215, 198, 244, 66, 233, 255, 83, 158, 17, 52, 36, 27, 254, 157, 207, 20, 229, 2, 17, 0, 0, 0, 1, 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