Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322c654ec53ac253ce645dcf8e8131cebe4dca6ffd064ea35281f495c2ea8ff5

Tx prefix hash: 660a0a77dc48b3a6fdfc03e87d38290fe69a6abba4069c3d711fe9c460e29ed4
Tx public key: bee24410b852dd1cc46c8437fc52b27feaa3a01ddb8f4a3b4a26cabf04b313e0
Timestamp: 1699460693 Timestamp [UCT]: 2023-11-08 16:24:53 Age [y:d:h:m:s]: 01:076:16:56:58
Block: 887279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316191 RingCT/type: yes/0
Extra: 01bee24410b852dd1cc46c8437fc52b27feaa3a01ddb8f4a3b4a26cabf04b313e002110000000cfaf35c9c000000000000000000

1 output(s) for total of 0.704816963000 dcy

stealth address amount amount idx
00: 3b3206a453c4c0a1311e70910472cb278086cf6b801ae2fb73ce031a85418a24 0.704816963000 1343148 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": 887289, "vin": [ { "gen": { "height": 887279 } } ], "vout": [ { "amount": 704816963, "target": { "key": "3b3206a453c4c0a1311e70910472cb278086cf6b801ae2fb73ce031a85418a24" } } ], "extra": [ 1, 190, 226, 68, 16, 184, 82, 221, 28, 196, 108, 132, 55, 252, 82, 178, 127, 234, 163, 160, 29, 219, 143, 74, 59, 74, 38, 202, 191, 4, 179, 19, 224, 2, 17, 0, 0, 0, 12, 250, 243, 92, 156, 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