Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b947abdd170cac0a5d73fc09c2f2c889b3869a0f31333746381ce7eb61c6568c

Tx prefix hash: 98dfbf289c325c970a81fa8dbec38fd64a49d6200f3f1fca0a43397295db4dd6
Tx public key: 1e663fa80ebae10892618e85db9cf4e38437ed8dc30a22f4dee7050c44ce532c
Timestamp: 1709151499 Timestamp [UCT]: 2024-02-28 20:18:19 Age [y:d:h:m:s]: 01:259:12:34:07
Block: 967621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444219 RingCT/type: yes/0
Extra: 011e663fa80ebae10892618e85db9cf4e38437ed8dc30a22f4dee7050c44ce532c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fbf1f151f1d8b0985eca665cc9263b2141401c3708badfbc51e13fbae221ba5 0.600000000000 1427404 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": 967631, "vin": [ { "gen": { "height": 967621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fbf1f151f1d8b0985eca665cc9263b2141401c3708badfbc51e13fbae221ba5" } } ], "extra": [ 1, 30, 102, 63, 168, 14, 186, 225, 8, 146, 97, 142, 133, 219, 156, 244, 227, 132, 55, 237, 141, 195, 10, 34, 244, 222, 231, 5, 12, 68, 206, 83, 44, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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