Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bba00965de740bd9ba645718ec184e1fa1c05a13e5363b0cf373fef4a58fe04

Tx prefix hash: b8dc03a58818aa13bc7e2f6d94e7ea91724d5f2b6f575d78833585679718df65
Tx public key: 4f3b64242a59376b4114d3a55354ac72f6777a92968eb469f7cee5e5a96cf660
Timestamp: 1732714990 Timestamp [UCT]: 2024-11-27 13:43:10 Age [y:d:h:m:s]: 00:128:00:46:25
Block: 1162872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91313 RingCT/type: yes/0
Extra: 014f3b64242a59376b4114d3a55354ac72f6777a92968eb469f7cee5e5a96cf660021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a434897ded420ad9d8fedb568d067a4b0852a4dac0e14e1e2c6c18524aa9bc56 0.600000000000 1648535 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": 1162882, "vin": [ { "gen": { "height": 1162872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a434897ded420ad9d8fedb568d067a4b0852a4dac0e14e1e2c6c18524aa9bc56" } } ], "extra": [ 1, 79, 59, 100, 36, 42, 89, 55, 107, 65, 20, 211, 165, 83, 84, 172, 114, 246, 119, 122, 146, 150, 142, 180, 105, 247, 206, 229, 229, 169, 108, 246, 96, 2, 17, 0, 0, 0, 2, 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