Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e43538bc852022cc06643ec083a7cbeaf74d76ce6384fd60970051d0a5926b7b

Tx prefix hash: b28e14121f700116e8e4fb3c8aaa2e614f191993d30c56f35992a59e35b0cb96
Tx public key: 4a91eb4c7fc8f8e9e5c9fe31a353f4d74be49e62bbc7ea0b5f7a9be2a7959bf3
Timestamp: 1726082258 Timestamp [UCT]: 2024-09-11 19:17:38 Age [y:d:h:m:s]: 00:041:09:08:03
Block: 1107973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29618 RingCT/type: yes/0
Extra: 014a91eb4c7fc8f8e9e5c9fe31a353f4d74be49e62bbc7ea0b5f7a9be2a7959bf302110000000391e13c04000000000000000000

1 output(s) for total of 0.607800000000 dcy

stealth address amount amount idx
00: 7041865deebc5b8c18e29f694d5d1b8a69beab36e886ac1c79177bf5ec4896af 0.607800000000 1585706 of 0

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": 1107983, "vin": [ { "gen": { "height": 1107973 } } ], "vout": [ { "amount": 607800000, "target": { "key": "7041865deebc5b8c18e29f694d5d1b8a69beab36e886ac1c79177bf5ec4896af" } } ], "extra": [ 1, 74, 145, 235, 76, 127, 200, 248, 233, 229, 201, 254, 49, 163, 83, 244, 215, 75, 228, 158, 98, 187, 199, 234, 11, 95, 122, 155, 226, 167, 149, 155, 243, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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