Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63439e42c46c775ad40beccb6662876123febfa6de71d1fb2a40ace60fedf3ca

Tx prefix hash: ab001df2eb91fd1abe5012bdcfe3a17472e677c0e2e0ff23f36a9cab98fc3b01
Tx public key: 86522d0cbc6885172848d43c8058acd8a6b9342ec7257008e37716b3dbf5a71c
Timestamp: 1695856559 Timestamp [UCT]: 2023-09-27 23:15:59 Age [y:d:h:m:s]: 01:247:08:30:05
Block: 857595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437899 RingCT/type: yes/0
Extra: 0186522d0cbc6885172848d43c8058acd8a6b9342ec7257008e37716b3dbf5a71c02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.883958357000 dcy

stealth address amount amount idx
00: f7a2b91076cf6ad7989b7f73f08d04b20830351a880b1cf4c0e667c3d9dc23a4 0.883958357000 1311733 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": 857605, "vin": [ { "gen": { "height": 857595 } } ], "vout": [ { "amount": 883958357, "target": { "key": "f7a2b91076cf6ad7989b7f73f08d04b20830351a880b1cf4c0e667c3d9dc23a4" } } ], "extra": [ 1, 134, 82, 45, 12, 188, 104, 133, 23, 40, 72, 212, 60, 128, 88, 172, 216, 166, 185, 52, 46, 199, 37, 112, 8, 227, 119, 22, 179, 219, 245, 167, 28, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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