Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3144b255d0d7312debcec51d0793adfcec4fbb95b01950c5a6d913e7aabc27

Tx prefix hash: 142711aff6e028152ceedbd5877770c90eeb005d4eee6f6e21f10b66f0107645
Tx public key: a7c13440fb24a8c50f6da06a6e8a0972ee9dd8832f52d525e73ac6829d30161c
Timestamp: 1578443968 Timestamp [UCT]: 2020-01-08 00:39:28 Age [y:d:h:m:s]: 04:303:13:03:07
Block: 40878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106240 RingCT/type: yes/0
Extra: 01a7c13440fb24a8c50f6da06a6e8a0972ee9dd8832f52d525e73ac6829d30161c021100000002b221b3d1000000000000000000

1 output(s) for total of 449.319289098000 dcy

stealth address amount amount idx
00: 78164faa404361bbe98d0760a126e3a93bc850dc8458633caf4497b855924789 449.319289098000 72266 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": 40888, "vin": [ { "gen": { "height": 40878 } } ], "vout": [ { "amount": 449319289098, "target": { "key": "78164faa404361bbe98d0760a126e3a93bc850dc8458633caf4497b855924789" } } ], "extra": [ 1, 167, 193, 52, 64, 251, 36, 168, 197, 15, 109, 160, 106, 110, 138, 9, 114, 238, 157, 216, 131, 47, 82, 213, 37, 231, 58, 198, 130, 157, 48, 22, 28, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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