Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d7cd56c841084508d8959e8b0940dd8e8d9d07fef607443fae5580873943ef0

Tx prefix hash: 4558eee8bf5ac65b360c6b84d3f540ecb454c172b1207538d730a91d3b8cfb00
Tx public key: d904811306f975e4c17f916c885ee5be5398cf4c9bba60bae196c8c8cf82ebd3
Timestamp: 1720386134 Timestamp [UCT]: 2024-07-07 21:02:14 Age [y:d:h:m:s]: 00:230:21:36:43
Block: 1060750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164935 RingCT/type: yes/0
Extra: 01d904811306f975e4c17f916c885ee5be5398cf4c9bba60bae196c8c8cf82ebd302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a4e8a80814b2e11faaca4345d5f9fd3dafbb0c44c804a798b4b02982ac98fee 0.600000000000 1531235 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": 1060760, "vin": [ { "gen": { "height": 1060750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a4e8a80814b2e11faaca4345d5f9fd3dafbb0c44c804a798b4b02982ac98fee" } } ], "extra": [ 1, 217, 4, 129, 19, 6, 249, 117, 228, 193, 127, 145, 108, 136, 94, 229, 190, 83, 152, 207, 76, 155, 186, 96, 186, 225, 150, 200, 200, 207, 130, 235, 211, 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