Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0e1f10d8fbeee01414c9a5ffb7b53bea1e05fe544d3597e2926654802c0baa

Tx prefix hash: afe9e3398c8ed21306268b1587993f47cb4301d9266f4ebb7b4d9df69787803e
Tx public key: 7671c2f5023da1d3799e4bc89a500e63848c4a32dd90aaa7049ef97ee0d2aa78
Timestamp: 1733376976 Timestamp [UCT]: 2024-12-05 05:36:16 Age [y:d:h:m:s]: 00:195:01:27:24
Block: 1168355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139140 RingCT/type: yes/0
Extra: 017671c2f5023da1d3799e4bc89a500e63848c4a32dd90aaa7049ef97ee0d2aa780211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86db817ac992356ca8d2927e9595b113d39b7810016e7e3d2aa0867ce955a0f4 0.600000000000 1654064 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": 1168365, "vin": [ { "gen": { "height": 1168355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86db817ac992356ca8d2927e9595b113d39b7810016e7e3d2aa0867ce955a0f4" } } ], "extra": [ 1, 118, 113, 194, 245, 2, 61, 161, 211, 121, 158, 75, 200, 154, 80, 14, 99, 132, 140, 74, 50, 221, 144, 170, 167, 4, 158, 249, 126, 224, 210, 170, 120, 2, 17, 0, 0, 0, 1, 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