Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63b9e666e846d8c99c7bdaa76a7aaaa3548169c9aaa7a8dde00505d6f9cda524

Tx prefix hash: 1918d02d27316caf880c1cae9b3424537b0e5d59f988539f0fa290e1da305873
Tx public key: 447141caf27564da9b47f4a268274e38a78a1491bdcb79ec79ea895293299d45
Timestamp: 1696528152 Timestamp [UCT]: 2023-10-05 17:49:12 Age [y:d:h:m:s]: 01:041:17:49:44
Block: 863164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291055 RingCT/type: yes/0
Extra: 01447141caf27564da9b47f4a268274e38a78a1491bdcb79ec79ea895293299d4502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.847187207000 dcy

stealth address amount amount idx
00: 41873565d0cc24214a71ccd9b6edd7a38e21b8e4fbcd33ee2997c3eb9c19812a 0.847187207000 1317612 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": 863174, "vin": [ { "gen": { "height": 863164 } } ], "vout": [ { "amount": 847187207, "target": { "key": "41873565d0cc24214a71ccd9b6edd7a38e21b8e4fbcd33ee2997c3eb9c19812a" } } ], "extra": [ 1, 68, 113, 65, 202, 242, 117, 100, 218, 155, 71, 244, 162, 104, 39, 78, 56, 167, 138, 20, 145, 189, 203, 121, 236, 121, 234, 137, 82, 147, 41, 157, 69, 2, 17, 0, 0, 0, 5, 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