Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39e59927f666826a3c7d801604d808d07a8039e3bc67a1f742d1834c9a092b72

Tx prefix hash: 876378c3022a72b9f66a166a855a0dba711872de046700b4d4e44c5e755d481f
Tx public key: 938b9a155021e4887a0f0ac2fe1dad9583187a30fb732b2c15977e40a6a1a938
Timestamp: 1736279166 Timestamp [UCT]: 2025-01-07 19:46:06 Age [y:d:h:m:s]: 00:086:04:36:54
Block: 1192383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61386 RingCT/type: yes/0
Extra: 01938b9a155021e4887a0f0ac2fe1dad9583187a30fb732b2c15977e40a6a1a938021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42836139d35abf0cb6e1c461c249af2fdf9d67490f46d99f09659af8abeceed6 0.600000000000 1678934 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": 1192393, "vin": [ { "gen": { "height": 1192383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42836139d35abf0cb6e1c461c249af2fdf9d67490f46d99f09659af8abeceed6" } } ], "extra": [ 1, 147, 139, 154, 21, 80, 33, 228, 136, 122, 15, 10, 194, 254, 29, 173, 149, 131, 24, 122, 48, 251, 115, 43, 44, 21, 151, 126, 64, 166, 161, 169, 56, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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