Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ededd87eaecb280f5e1035bf6d992c217b660f289d531d1a8afbbc0bbcb83842

Tx prefix hash: 5d0ce1c6a044df91c2a75a116bf0fd0a501f83f9dcb40e262a0700fc7f52f80c
Tx public key: bb4ea8390b3eee7a008b3585a39379c1cad5c0337276a28ff45b461829969620
Timestamp: 1763582377 Timestamp [UCT]: 2025-11-19 19:59:37 Age [y:d:h:m:s]: 00:007:14:16:17
Block: 1415745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5443 RingCT/type: yes/0
Extra: 01bb4ea8390b3eee7a008b3585a39379c1cad5c0337276a28ff45b461829969620021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e307fb90a3d1ec6e515a9847539011696223e2ce5e86c3099f7e1a499594ab27 0.600000000000 1904252 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": 1415755, "vin": [ { "gen": { "height": 1415745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e307fb90a3d1ec6e515a9847539011696223e2ce5e86c3099f7e1a499594ab27" } } ], "extra": [ 1, 187, 78, 168, 57, 11, 62, 238, 122, 0, 139, 53, 133, 163, 147, 121, 193, 202, 213, 192, 51, 114, 118, 162, 143, 244, 91, 70, 24, 41, 150, 150, 32, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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