Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40acf084561dd4f37837ab0b4241246a7e25313de99930d83816c2ee7550f0f9

Tx prefix hash: ea5f4bb6697b598033812fc20b8464a29d3cc468243ff694c62f7ccebe1d5661
Tx public key: 022e5028e28c77afef1e4b0ae3fc0c4fe6d9489a3fdbe0c0821cfee0794905aa
Timestamp: 1725883698 Timestamp [UCT]: 2024-09-09 12:08:18 Age [y:d:h:m:s]: 00:212:10:05:44
Block: 1106342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151645 RingCT/type: yes/0
Extra: 01022e5028e28c77afef1e4b0ae3fc0c4fe6d9489a3fdbe0c0821cfee0794905aa02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65cdb91a8467be860967747ab051499d13e74798cad7b592972e8c5a23a9334f 0.600000000000 1583941 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": 1106352, "vin": [ { "gen": { "height": 1106342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65cdb91a8467be860967747ab051499d13e74798cad7b592972e8c5a23a9334f" } } ], "extra": [ 1, 2, 46, 80, 40, 226, 140, 119, 175, 239, 30, 75, 10, 227, 252, 12, 79, 230, 217, 72, 154, 63, 219, 224, 192, 130, 28, 254, 224, 121, 73, 5, 170, 2, 17, 0, 0, 0, 10, 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