Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91c496b5ff4c0295cbd6b222cb7ab0626b5a24f0cb0b5081d727c356e7000d7f

Tx prefix hash: 039bbc05aedaef0d704be242207ac3c321ca0bdc3ec94b4ef2c8a0ae4eba5643
Tx public key: d225c8bd5998bdcf10f5b102734786ee5e3f9f8831695668ed9821b92d4b1737
Timestamp: 1701683081 Timestamp [UCT]: 2023-12-04 09:44:41 Age [y:d:h:m:s]: 01:129:06:15:54
Block: 905687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353559 RingCT/type: yes/0
Extra: 01d225c8bd5998bdcf10f5b102734786ee5e3f9f8831695668ed9821b92d4b173702110000000333af99f4000000000000000000

1 output(s) for total of 0.612467398000 dcy

stealth address amount amount idx
00: 16af6c1a6d64b4539b2d4d01790ddfcd28a94a846f1d2491042e6c4e8f00483c 0.612467398000 1362584 of 0

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": 905697, "vin": [ { "gen": { "height": 905687 } } ], "vout": [ { "amount": 612467398, "target": { "key": "16af6c1a6d64b4539b2d4d01790ddfcd28a94a846f1d2491042e6c4e8f00483c" } } ], "extra": [ 1, 210, 37, 200, 189, 89, 152, 189, 207, 16, 245, 177, 2, 115, 71, 134, 238, 94, 63, 159, 136, 49, 105, 86, 104, 237, 152, 33, 185, 45, 75, 23, 55, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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