Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daedd4a9b059c11ce95caa670bcf63d969e2e1956262d9f13e74b8a8880aa2b9

Tx prefix hash: 8f98afd30b1f2f345ab5ba888492ff49a0153da1006068d863c3ea593dff1dcc
Tx public key: 0fd6dd76c1e792f9109e8213ca81eaf2da5a88b0c604eb2d5798cf4287f44256
Timestamp: 1670328444 Timestamp [UCT]: 2022-12-06 12:07:24 Age [y:d:h:m:s]: 02:041:08:38:44
Block: 646645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551479 RingCT/type: yes/0
Extra: 010fd6dd76c1e792f9109e8213ca81eaf2da5a88b0c604eb2d5798cf4287f4425602110000000183600029000000000000000000

1 output(s) for total of 4.419739486000 dcy

stealth address amount amount idx
00: 6384f822bbf5245a5c6e16f57759cdabc4b0c55e570c362bc34ea540595b862b 4.419739486000 1086880 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": 646655, "vin": [ { "gen": { "height": 646645 } } ], "vout": [ { "amount": 4419739486, "target": { "key": "6384f822bbf5245a5c6e16f57759cdabc4b0c55e570c362bc34ea540595b862b" } } ], "extra": [ 1, 15, 214, 221, 118, 193, 231, 146, 249, 16, 158, 130, 19, 202, 129, 234, 242, 218, 90, 136, 176, 198, 4, 235, 45, 87, 152, 207, 66, 135, 244, 66, 86, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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