Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7801401bb1abffc434d28e64605d8ae1144fe053a6f4cf4897e6b33f7de845

Tx prefix hash: 893f49d82684ce7f80b7c9028cedc8e537ee2c8ac159b1624ef8f3e9157fcec0
Tx public key: 7c814fe4bf621df23b7d71f3989273cbb559153d380b598a5aa8901bdecb34a1
Timestamp: 1713421033 Timestamp [UCT]: 2024-04-18 06:17:13 Age [y:d:h:m:s]: 01:200:01:51:54
Block: 1002993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401669 RingCT/type: yes/0
Extra: 017c814fe4bf621df23b7d71f3989273cbb559153d380b598a5aa8901bdecb34a10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e75681f24f5d96b261f23bb49bba8f37c4188236e84c3980f08f6d138b12bce9 0.600000000000 1463523 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": 1003003, "vin": [ { "gen": { "height": 1002993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e75681f24f5d96b261f23bb49bba8f37c4188236e84c3980f08f6d138b12bce9" } } ], "extra": [ 1, 124, 129, 79, 228, 191, 98, 29, 242, 59, 125, 113, 243, 152, 146, 115, 203, 181, 89, 21, 61, 56, 11, 89, 138, 90, 168, 144, 27, 222, 203, 52, 161, 2, 17, 0, 0, 0, 4, 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