Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6b5026a68a12f9a65f00c47754789a7e7714c3bfd163432bf3ec6eab4ec7e7

Tx prefix hash: 8c34a9b7bab011bf315a0489127e58d04342f32e25cbf0a0bf7291117829fa8d
Tx public key: d685c10fe241f4933b07e685b9fc9aae8b3535ed238d61c413ee8c30a19a2577
Timestamp: 1729414475 Timestamp [UCT]: 2024-10-20 08:54:35 Age [y:d:h:m:s]: 00:170:18:48:01
Block: 1135597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121835 RingCT/type: yes/0
Extra: 01d685c10fe241f4933b07e685b9fc9aae8b3535ed238d61c413ee8c30a19a2577021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160ecf1d15263802f731669766d0ed095b65d7a4362a472c7f5a58ea73345024 0.600000000000 1618936 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": 1135607, "vin": [ { "gen": { "height": 1135597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160ecf1d15263802f731669766d0ed095b65d7a4362a472c7f5a58ea73345024" } } ], "extra": [ 1, 214, 133, 193, 15, 226, 65, 244, 147, 59, 7, 230, 133, 185, 252, 154, 174, 139, 53, 53, 237, 35, 141, 97, 196, 19, 238, 140, 48, 161, 154, 37, 119, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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