Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a99ec15ed5db95c940376da5b2595be5fed331a4076788befdf2e46a623debcf

Tx prefix hash: 3e2d3af6cbcaeaf6e399229962c67176e3f89715c5eebcd8e22c7493bcfcd17b
Tx public key: 9e69c6e8712725a05d5a4eab8f8e4b350391487de6c6a46aa0c0b3896802cece
Timestamp: 1727088624 Timestamp [UCT]: 2024-09-23 10:50:24 Age [y:d:h:m:s]: 00:045:14:53:06
Block: 1116320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32591 RingCT/type: yes/0
Extra: 019e69c6e8712725a05d5a4eab8f8e4b350391487de6c6a46aa0c0b3896802cece021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8576636a4c103c57e223714ae79dcd7556a2983fb1966766cfdf411b7b542777 0.600000000000 1596763 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": 1116330, "vin": [ { "gen": { "height": 1116320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8576636a4c103c57e223714ae79dcd7556a2983fb1966766cfdf411b7b542777" } } ], "extra": [ 1, 158, 105, 198, 232, 113, 39, 37, 160, 93, 90, 78, 171, 143, 142, 75, 53, 3, 145, 72, 125, 230, 198, 164, 106, 160, 192, 179, 137, 104, 2, 206, 206, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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