Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acf8dbfbf91dbd5119727d148b0b543c6864fbf8519e329647c1252b64916c7d

Tx prefix hash: e0cc6fb3b956e75a2ed3f5876f89e840787fda908bea379107b51df0516c8657
Tx public key: 7d8c2a5b9fc1b743047e1146e722d8bd78af0008fed8ad36433c461e7701b97b
Timestamp: 1755001532 Timestamp [UCT]: 2025-08-12 12:25:32 Age [y:d:h:m:s]: 00:054:12:57:48
Block: 1345444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38237 RingCT/type: yes/0
Extra: 017d8c2a5b9fc1b743047e1146e722d8bd78af0008fed8ad36433c461e7701b97b021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79f7f0a1da1d02cbc981f116f0b7b8335c8e34a4d0ad5f11371cca7a365d46a4 0.600000000000 1833337 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": 1345454, "vin": [ { "gen": { "height": 1345444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79f7f0a1da1d02cbc981f116f0b7b8335c8e34a4d0ad5f11371cca7a365d46a4" } } ], "extra": [ 1, 125, 140, 42, 91, 159, 193, 183, 67, 4, 126, 17, 70, 231, 34, 216, 189, 120, 175, 0, 8, 254, 216, 173, 54, 67, 60, 70, 30, 119, 1, 185, 123, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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