Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 478c101332333ef85812148c42ce1fbadd0123b9a0c3c362befb039c3a440d4c

Tx prefix hash: ca9dccffa1966b3901e41770aa5acb44c5e66d3f2293d60ba25535840f4059c0
Tx public key: 7d8b24b410d2c569ea1316083dfd9a5b843a35386bc296297e9a22b2eaf97550
Timestamp: 1736757393 Timestamp [UCT]: 2025-01-13 08:36:33 Age [y:d:h:m:s]: 00:065:02:24:41
Block: 1196340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46320 RingCT/type: yes/0
Extra: 017d8b24b410d2c569ea1316083dfd9a5b843a35386bc296297e9a22b2eaf97550021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38d5a3e1201684e0540474f3f8e6c789fd73ea78c15d0eaf5c53e031cb4c463e 0.600000000000 1682939 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": 1196350, "vin": [ { "gen": { "height": 1196340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38d5a3e1201684e0540474f3f8e6c789fd73ea78c15d0eaf5c53e031cb4c463e" } } ], "extra": [ 1, 125, 139, 36, 180, 16, 210, 197, 105, 234, 19, 22, 8, 61, 253, 154, 91, 132, 58, 53, 56, 107, 194, 150, 41, 126, 154, 34, 178, 234, 249, 117, 80, 2, 17, 0, 0, 0, 6, 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