Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6db154ce85af2af2e7c20dec317abc635636b4572ee9d1608c5f4f972d7413e

Tx prefix hash: 53f26ecc4bd74cc78d65af61131b41661844254bab2a51931a052455b087259c
Tx public key: 31283cabe3ea0ce01efb51dbb4f48c8a479f9296b4590fe2a2f25b5de4ad21c5
Timestamp: 1747649650 Timestamp [UCT]: 2025-05-19 10:14:10 Age [y:d:h:m:s]: 00:141:16:32:57
Block: 1286247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98903 RingCT/type: yes/0
Extra: 0131283cabe3ea0ce01efb51dbb4f48c8a479f9296b4590fe2a2f25b5de4ad21c502110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d4dab3d1e479e5e518c716a1a222cf3eeb70151d9491a2df5ed43082431617f 0.600000000000 1773712 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": 1286257, "vin": [ { "gen": { "height": 1286247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d4dab3d1e479e5e518c716a1a222cf3eeb70151d9491a2df5ed43082431617f" } } ], "extra": [ 1, 49, 40, 60, 171, 227, 234, 12, 224, 30, 251, 81, 219, 180, 244, 140, 138, 71, 159, 146, 150, 180, 89, 15, 226, 162, 242, 91, 93, 228, 173, 33, 197, 2, 17, 0, 0, 0, 10, 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