Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825b3bad4c76efccdf8e2fe6cc4424ed40bb3162bda0d1143b8d57ab8f27fe1b

Tx prefix hash: 498f942a005496f78bc0557db16010c57b0806da93c4728831d31822de1df54a
Tx public key: 2eacba0aa81dc2c89fa2f6015611cd3945ea0bf7d54270b7d64e100ebac1e2f2
Timestamp: 1763142115 Timestamp [UCT]: 2025-11-14 17:41:55 Age [y:d:h:m:s]: 00:050:22:19:11
Block: 1412098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36483 RingCT/type: yes/0
Extra: 012eacba0aa81dc2c89fa2f6015611cd3945ea0bf7d54270b7d64e100ebac1e2f2021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dffc04007d76356dcedbb6fea0541d7492cc8d47a3223e1a60672e28cbcfb788 0.600000000000 1900563 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": 1412108, "vin": [ { "gen": { "height": 1412098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dffc04007d76356dcedbb6fea0541d7492cc8d47a3223e1a60672e28cbcfb788" } } ], "extra": [ 1, 46, 172, 186, 10, 168, 29, 194, 200, 159, 162, 246, 1, 86, 17, 205, 57, 69, 234, 11, 247, 213, 66, 112, 183, 214, 78, 16, 14, 186, 193, 226, 242, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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