Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b83889e2e4a78d60a1dc87911fe40952832badfd7dcb3357232369ba3b1388a8

Tx prefix hash: 0ef34b35a723e667b7a5859e5180f4a5ae6f6eb790b79cdd0e5604058791058e
Tx public key: 03758c968d3ff102e2ad6d9fc3308c0300e27722a8b166f4fff3d984d3057688
Timestamp: 1726135776 Timestamp [UCT]: 2024-09-12 10:09:36 Age [y:d:h:m:s]: 00:101:09:39:38
Block: 1108421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72546 RingCT/type: yes/0
Extra: 0103758c968d3ff102e2ad6d9fc3308c0300e27722a8b166f4fff3d984d3057688021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1da464d0bc84667ee74c1af8f152861fdd28818c66c7f4b2382fee31df7198e 0.600000000000 1586308 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": 1108431, "vin": [ { "gen": { "height": 1108421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1da464d0bc84667ee74c1af8f152861fdd28818c66c7f4b2382fee31df7198e" } } ], "extra": [ 1, 3, 117, 140, 150, 141, 63, 241, 2, 226, 173, 109, 159, 195, 48, 140, 3, 0, 226, 119, 34, 168, 177, 102, 244, 255, 243, 217, 132, 211, 5, 118, 136, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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