Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e407dd447cb51f66a0903dfd79f2aa38b2a72af8409a0c43204ce78f94432e8

Tx prefix hash: 174c60a97fef849aeba1ab1b242cc64785f334dc294ba8ff906d2b888e5483b4
Tx public key: af4b155b94193bfffb1bf4bbf0839a59d4b8a88ce99279f040fd3107b9890dac
Timestamp: 1761103594 Timestamp [UCT]: 2025-10-22 03:26:34 Age [y:d:h:m:s]: 00:098:10:33:36
Block: 1395211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70301 RingCT/type: yes/0
Extra: 01af4b155b94193bfffb1bf4bbf0839a59d4b8a88ce99279f040fd3107b9890dac02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da8289f2efa14fdc389ecd15b6f819a18d5e3f8ba43a2a89ddec5039dc0558b 0.600000000000 1883488 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": 1395221, "vin": [ { "gen": { "height": 1395211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da8289f2efa14fdc389ecd15b6f819a18d5e3f8ba43a2a89ddec5039dc0558b" } } ], "extra": [ 1, 175, 75, 21, 91, 148, 25, 59, 255, 251, 27, 244, 187, 240, 131, 154, 89, 212, 184, 168, 140, 233, 146, 121, 240, 64, 253, 49, 7, 185, 137, 13, 172, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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