Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b06b39ec4432b35f6d7e2d56cf4c6051269c71a981095a431dc35caca64fbe

Tx prefix hash: f56cb96953be06de45a3b56285a3d8593a1c68c6cba9e92c5eee118b937aa8e8
Tx public key: 91908e95da37088de577c12902fb6b683587756293be4be2f59a4a02c5fa0965
Timestamp: 1693387714 Timestamp [UCT]: 2023-08-30 09:28:34 Age [y:d:h:m:s]: 01:094:02:04:01
Block: 837105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328570 RingCT/type: yes/0
Extra: 0191908e95da37088de577c12902fb6b683587756293be4be2f59a4a02c5fa09650211000000191656a529000000000000000000

1 output(s) for total of 1.033531486000 dcy

stealth address amount amount idx
00: bf8a4e0301a46f53e04a427616b3c732c56b3a6f3fd97a81dd29091e3be48ee7 1.033531486000 1289717 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": 837115, "vin": [ { "gen": { "height": 837105 } } ], "vout": [ { "amount": 1033531486, "target": { "key": "bf8a4e0301a46f53e04a427616b3c732c56b3a6f3fd97a81dd29091e3be48ee7" } } ], "extra": [ 1, 145, 144, 142, 149, 218, 55, 8, 141, 229, 119, 193, 41, 2, 251, 107, 104, 53, 135, 117, 98, 147, 190, 75, 226, 245, 154, 74, 2, 197, 250, 9, 101, 2, 17, 0, 0, 0, 25, 22, 86, 165, 41, 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