Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66c0e6a45a402660dcef493a6682f03f3c94638cb34372c34d314e3a050f8ecf

Tx prefix hash: 6076343100d2ccccbcbc3f8989866acb4fc192d1dd69414ee60c7720d9c689dc
Tx public key: 0a1fc2e914600b5d98a46be8ac02bb8054813b88929baedc07a472a728481e31
Timestamp: 1676854801 Timestamp [UCT]: 2023-02-20 01:00:01 Age [y:d:h:m:s]: 02:006:06:40:41
Block: 700741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526040 RingCT/type: yes/0
Extra: 010a1fc2e914600b5d98a46be8ac02bb8054813b88929baedc07a472a728481e31021100000001835e4d22000000000000000000

1 output(s) for total of 2.925190052000 dcy

stealth address amount amount idx
00: 4b189d5ef57b3a137a15e75606f4cbea6c560f7b08414cefb4c48dc6fde16417 2.925190052000 1144192 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": 700751, "vin": [ { "gen": { "height": 700741 } } ], "vout": [ { "amount": 2925190052, "target": { "key": "4b189d5ef57b3a137a15e75606f4cbea6c560f7b08414cefb4c48dc6fde16417" } } ], "extra": [ 1, 10, 31, 194, 233, 20, 96, 11, 93, 152, 164, 107, 232, 172, 2, 187, 128, 84, 129, 59, 136, 146, 155, 174, 220, 7, 164, 114, 167, 40, 72, 30, 49, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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