Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7efb1d7054cada034dff450dd55bf4704f20215d9ee3a983c9fd4e1bac2f605b

Tx prefix hash: e428af6fa28401dd288d25ee1e97daa910e929c5ca231f9b5c955963f3bf3c7f
Tx public key: 7a546aa62f3d653a2c13d4e556f4dc13c853ce5f99ce611a1d2821514016ae10
Timestamp: 1751381303 Timestamp [UCT]: 2025-07-01 14:48:23 Age [y:d:h:m:s]: 00:135:19:57:18
Block: 1316600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95293 RingCT/type: yes/0
Extra: 017a546aa62f3d653a2c13d4e556f4dc13c853ce5f99ce611a1d2821514016ae10021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99e234087b320bd80297d035f49b8d781a69c2f7798a4e9bc41c29f217f920e1 0.600000000000 1804261 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": 1316610, "vin": [ { "gen": { "height": 1316600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99e234087b320bd80297d035f49b8d781a69c2f7798a4e9bc41c29f217f920e1" } } ], "extra": [ 1, 122, 84, 106, 166, 47, 61, 101, 58, 44, 19, 212, 229, 86, 244, 220, 19, 200, 83, 206, 95, 153, 206, 97, 26, 29, 40, 33, 81, 64, 22, 174, 16, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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