Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042eac55836d38a7859ca6ec5739aa5ca5c4ced21639b328a2bff7d593bcaba8

Tx prefix hash: 52fdc31483fa0e214c41b7a9f0426146c3b5d202fca319848d19252d82732067
Tx public key: 42b7963d41d9bea5533991311050f24d3b64678e2f8a0dd817f07de6a55001aa
Timestamp: 1641079874 Timestamp [UCT]: 2022-01-01 23:31:14 Age [y:d:h:m:s]: 03:132:09:55:47
Block: 408474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 873460 RingCT/type: yes/0
Extra: 0142b7963d41d9bea5533991311050f24d3b64678e2f8a0dd817f07de6a55001aa021100000026e2bb00ee000000000000000000

1 output(s) for total of 27.199217593000 dcy

stealth address amount amount idx
00: 7f3c64f5ee37fbfc64f5d88053eee62711275db34dacd97fc75fc0a6ef385b47 27.199217593000 810539 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": 408484, "vin": [ { "gen": { "height": 408474 } } ], "vout": [ { "amount": 27199217593, "target": { "key": "7f3c64f5ee37fbfc64f5d88053eee62711275db34dacd97fc75fc0a6ef385b47" } } ], "extra": [ 1, 66, 183, 150, 61, 65, 217, 190, 165, 83, 57, 145, 49, 16, 80, 242, 77, 59, 100, 103, 142, 47, 138, 13, 216, 23, 240, 125, 230, 165, 80, 1, 170, 2, 17, 0, 0, 0, 38, 226, 187, 0, 238, 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