Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5198ead3854d41e7b81effa1ca646cb3660cc9dc0bf06964731d63dfcdd4e40

Tx prefix hash: 0becf1c77657e3084d5d20fffdfd411ace56a7d880e2af61d62592f32f672fe5
Tx public key: 4417ecb307aa7c1e0d755f4c6ef11fc7e92749381e485cc7e62a5649ce36405d
Timestamp: 1709994802 Timestamp [UCT]: 2024-03-09 14:33:22 Age [y:d:h:m:s]: 01:066:19:09:07
Block: 974612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308756 RingCT/type: yes/0
Extra: 014417ecb307aa7c1e0d755f4c6ef11fc7e92749381e485cc7e62a5649ce36405d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4aae3b66171edbeab57433367f8bb6285aa9f143bf15add9c635b23d94b08fe 0.600000000000 1434571 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": 974622, "vin": [ { "gen": { "height": 974612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4aae3b66171edbeab57433367f8bb6285aa9f143bf15add9c635b23d94b08fe" } } ], "extra": [ 1, 68, 23, 236, 179, 7, 170, 124, 30, 13, 117, 95, 76, 110, 241, 31, 199, 233, 39, 73, 56, 30, 72, 92, 199, 230, 42, 86, 73, 206, 54, 64, 93, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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