Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3441409ad7ecfdac7c09e63781ec8bce5c7b09da1bae263aca88fff223fd1b0d

Tx prefix hash: 2f999046f511b3f5a79b0eb0613068e07f72cb69fd47183f62d37a12fd2138f5
Tx public key: 99a8e803bc5576629555abefac07c32579726db4c8ebc126839c545165a90c2c
Timestamp: 1754272014 Timestamp [UCT]: 2025-08-04 01:46:54 Age [y:d:h:m:s]: 00:179:00:32:29
Block: 1339784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126813 RingCT/type: yes/0
Extra: 0199a8e803bc5576629555abefac07c32579726db4c8ebc126839c545165a90c2c021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feffdce58a69a3d8f5c01efb3a9a8d810d190c688a629a1c435d6dbba655b25d 0.600000000000 1827599 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": 1339794, "vin": [ { "gen": { "height": 1339784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feffdce58a69a3d8f5c01efb3a9a8d810d190c688a629a1c435d6dbba655b25d" } } ], "extra": [ 1, 153, 168, 232, 3, 188, 85, 118, 98, 149, 85, 171, 239, 172, 7, 195, 37, 121, 114, 109, 180, 200, 235, 193, 38, 131, 156, 84, 81, 101, 169, 12, 44, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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