Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50af86adf4471dd8cc1b0ed3a4877e5e09e50f5a657e5c312b198608a620d0c2

Tx prefix hash: 2f0cb3d4a96983aa6cfc718596083fa6b1613c2ec5ec4fd09d4d2cf06e72cbea
Tx public key: ad9c94e4058fed05a76f9abb287a383f71695225858cd6737e4e5ce4c789d0c2
Timestamp: 1728959214 Timestamp [UCT]: 2024-10-15 02:26:54 Age [y:d:h:m:s]: 00:099:15:55:38
Block: 1131830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71197 RingCT/type: yes/0
Extra: 01ad9c94e4058fed05a76f9abb287a383f71695225858cd6737e4e5ce4c789d0c2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e42f44712f35c5d5960d8d3ef02247014f6b7f05795505b672a486143b7c74a9 0.600000000000 1614737 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": 1131840, "vin": [ { "gen": { "height": 1131830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e42f44712f35c5d5960d8d3ef02247014f6b7f05795505b672a486143b7c74a9" } } ], "extra": [ 1, 173, 156, 148, 228, 5, 143, 237, 5, 167, 111, 154, 187, 40, 122, 56, 63, 113, 105, 82, 37, 133, 140, 214, 115, 126, 78, 92, 228, 199, 137, 208, 194, 2, 17, 0, 0, 0, 4, 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