Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4395e429c0fd459f42924f602bc1c706e1164c1e0280d48bfab16517693e75e

Tx prefix hash: a423c419d254b69f02a8e3caa2b5b86fa7d4a0ad764ecd21a4e540656f8b1a88
Tx public key: babf9d65f7dc58717000f2224c03a934c5ec0e403f24724575aa7e8484e32b83
Timestamp: 1742983588 Timestamp [UCT]: 2025-03-26 10:06:28 Age [y:d:h:m:s]: 00:238:21:55:01
Block: 1247603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168502 RingCT/type: yes/0
Extra: 01babf9d65f7dc58717000f2224c03a934c5ec0e403f24724575aa7e8484e32b83021100000001d2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 767b6c707377cd7a079ca6b42ee7e1fb29c380f5e8fae85615809fab5e2b1f0d 0.600000000000 1734626 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": 1247613, "vin": [ { "gen": { "height": 1247603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "767b6c707377cd7a079ca6b42ee7e1fb29c380f5e8fae85615809fab5e2b1f0d" } } ], "extra": [ 1, 186, 191, 157, 101, 247, 220, 88, 113, 112, 0, 242, 34, 76, 3, 169, 52, 197, 236, 14, 64, 63, 36, 114, 69, 117, 170, 126, 132, 132, 227, 43, 131, 2, 17, 0, 0, 0, 1, 210, 228, 14, 253, 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