Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ae7f2931391e5b14e6e44991ba99de865533aaf004ba7e1bb5edad54b82e032

Tx prefix hash: 3607c6fcf5b10181f6d00e6151ef67a3e05c8d678d731721fcdc482952e5df61
Tx public key: b95ed8f0e6d52e36d484ea8d31c1f027f26756a6544210ed00abcebb53e34886
Timestamp: 1736256676 Timestamp [UCT]: 2025-01-07 13:31:16 Age [y:d:h:m:s]: 00:089:03:11:34
Block: 1192198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63473 RingCT/type: yes/0
Extra: 01b95ed8f0e6d52e36d484ea8d31c1f027f26756a6544210ed00abcebb53e34886021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 630a0c06ce9a46e5f6f6c34dd66d6d49223cf5b0f0d49d5957b9e68554de982e 0.600000000000 1678747 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": 1192208, "vin": [ { "gen": { "height": 1192198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "630a0c06ce9a46e5f6f6c34dd66d6d49223cf5b0f0d49d5957b9e68554de982e" } } ], "extra": [ 1, 185, 94, 216, 240, 230, 213, 46, 54, 212, 132, 234, 141, 49, 193, 240, 39, 242, 103, 86, 166, 84, 66, 16, 237, 0, 171, 206, 187, 83, 227, 72, 134, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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