Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1a2d1f7cc71cb28adc49fc31367df272eee81a29d196f0e2ebf5d4ee23eedf6

Tx prefix hash: e71207f2f0cb22f0efa29dd67a4d0022b833b7f91866e92f05eaf0ed1ff279e5
Tx public key: b8f6d6a48bb13bd85c0118240333e4f5251cf6fef2b699397dc33c290587bdf9
Timestamp: 1763663610 Timestamp [UCT]: 2025-11-20 18:33:30 Age [y:d:h:m:s]: 00:037:17:14:01
Block: 1416409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27024 RingCT/type: yes/0
Extra: 01b8f6d6a48bb13bd85c0118240333e4f5251cf6fef2b699397dc33c290587bdf902110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 452437bf0a40ae3ccbced23acd3f99e44935760eccd08c33cd4956948e3aff9b 0.600000000000 1904928 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": 1416419, "vin": [ { "gen": { "height": 1416409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "452437bf0a40ae3ccbced23acd3f99e44935760eccd08c33cd4956948e3aff9b" } } ], "extra": [ 1, 184, 246, 214, 164, 139, 177, 59, 216, 92, 1, 24, 36, 3, 51, 228, 245, 37, 28, 246, 254, 242, 182, 153, 57, 125, 195, 60, 41, 5, 135, 189, 249, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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