Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1676b078595bdbf17c4217f3904b347c028affb6acd5a3578cf92db465489cbd

Tx prefix hash: fcb9e40e111383e3698bb4bff48c7bdd4ff6001b7e8c1ce40a35738d4c5f06a7
Tx public key: a2a55e9b962bbff884fdaddbf7476cb7f2d62a1c50d10e02fbc42ba8c74e03eb
Timestamp: 1737434345 Timestamp [UCT]: 2025-01-21 04:39:05 Age [y:d:h:m:s]: 00:148:09:37:50
Block: 1201896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105800 RingCT/type: yes/0
Extra: 01a2a55e9b962bbff884fdaddbf7476cb7f2d62a1c50d10e02fbc42ba8c74e03eb0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71cf7e16afefb91ba388dc25d4f8b552d4722211605f052ed92b371bc2c324d 0.600000000000 1688553 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": 1201906, "vin": [ { "gen": { "height": 1201896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71cf7e16afefb91ba388dc25d4f8b552d4722211605f052ed92b371bc2c324d" } } ], "extra": [ 1, 162, 165, 94, 155, 150, 43, 191, 248, 132, 253, 173, 219, 247, 71, 108, 183, 242, 214, 42, 28, 80, 209, 14, 2, 251, 196, 43, 168, 199, 78, 3, 235, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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