Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fe5a6a98f0a1af5e781f31177a4af628135fd4ebc807e36d709c69b34f5495c

Tx prefix hash: 861a2e7047317a5e2e921534ff23478e1119ad94e615609450502d7ffce2cb44
Tx public key: 3386aacac2a83cf00d397cfcbc33b3521e46b3a4708d48d0c7fd0784c35b76e8
Timestamp: 1755886316 Timestamp [UCT]: 2025-08-22 18:11:56 Age [y:d:h:m:s]: 00:039:01:03:23
Block: 1352150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27764 RingCT/type: yes/0
Extra: 013386aacac2a83cf00d397cfcbc33b3521e46b3a4708d48d0c7fd0784c35b76e80211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29ff418c0918e4d993b878d362f6afc808b72388748d87d10ed542e002c9274d 0.600000000000 1840113 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": 1352160, "vin": [ { "gen": { "height": 1352150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29ff418c0918e4d993b878d362f6afc808b72388748d87d10ed542e002c9274d" } } ], "extra": [ 1, 51, 134, 170, 202, 194, 168, 60, 240, 13, 57, 124, 252, 188, 51, 179, 82, 30, 70, 179, 164, 112, 141, 72, 208, 199, 253, 7, 132, 195, 91, 118, 232, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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