Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2122633e6f56700fec7c20b79efa9662729db7e5bf317ab61e6b11a05a1402cb

Tx prefix hash: 3fb0567bf7cf8719e9be2606ea59e6afdd2761b8c98d79d88c2dbc398aee399d
Tx public key: 8d95e9c7d2032b313f7d112490fb72f0af4a7a26e6dddaf131ec3a0659354632
Timestamp: 1723122170 Timestamp [UCT]: 2024-08-08 13:02:50 Age [y:d:h:m:s]: 00:232:12:13:34
Block: 1083437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166063 RingCT/type: yes/0
Extra: 018d95e9c7d2032b313f7d112490fb72f0af4a7a26e6dddaf131ec3a065935463202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f83409052b2f534370806c2057812c7cf5b4465f54d675897dec15a8d239b9e3 0.600000000000 1557356 of 15

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": 1083447, "vin": [ { "gen": { "height": 1083437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f83409052b2f534370806c2057812c7cf5b4465f54d675897dec15a8d239b9e3" } } ], "extra": [ 1, 141, 149, 233, 199, 210, 3, 43, 49, 63, 125, 17, 36, 144, 251, 114, 240, 175, 74, 122, 38, 230, 221, 218, 241, 49, 236, 58, 6, 89, 53, 70, 50, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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